SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
PHP

PHP static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your PHP code

  • All rules 273
  • Vulnerability42
  • Bug51
  • Security Hotspot34
  • Code Smell146
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Allowing unfiltered HTML content in WordPress is security-sensitive

           Security Hotspot
        4. Allowing unauthenticated database repair in WordPress is security-sensitive

           Security Hotspot
        5. Allowing all external requests from a WordPress server is security-sensitive

           Security Hotspot
        6. Disabling automatic updates is security-sensitive

           Security Hotspot
        7. WordPress theme and plugin editors are security-sensitive

           Security Hotspot
        8. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        9. Using clear-text protocols is security-sensitive

           Security Hotspot
        10. Manual generation of session ID is security-sensitive

           Security Hotspot
        11. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        12. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        13. Controlling permissions is security-sensitive

           Security Hotspot
        14. Reading the Standard Input is security-sensitive

           Security Hotspot
        15. Signaling processes is security-sensitive

           Security Hotspot
        16. Using command line arguments is security-sensitive

           Security Hotspot
        17. Using Sockets is security-sensitive

           Security Hotspot
        18. Configuring loggers is security-sensitive

           Security Hotspot
        19. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        20. Encrypting data is security-sensitive

           Security Hotspot
        21. Using regular expressions is security-sensitive

           Security Hotspot
        22. Deserializing objects from an untrusted source is security-sensitive

           Security Hotspot
        23. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        24. Disabling CSRF protections is security-sensitive

           Security Hotspot
        25. Creating cookies with broadly defined "domain" flags is security-sensitive

           Security Hotspot
        26. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        27. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        28. Writing cookies is security-sensitive

           Security Hotspot
        29. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        30. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        31. Formatting SQL queries is security-sensitive

           Security Hotspot
        32. Hard-coded credentials are security-sensitive

           Security Hotspot
        33. Dynamically executing code is security-sensitive

           Security Hotspot
        34. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Allowing all external requests from a WordPress server is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe

        External requests initiated by a WordPress server should be considered as security-sensitive. They may contain sensitive data which is stored in the files or in the database of the server. It’s important for the administrator of a WordPress server to understand what they contain and to which server they are sent.

        WordPress makes it possible to block external requests by setting the WP_HTTP_BLOCK_EXTERNAL option to true. It’s then possible to authorize requests to only a few servers using another option named WP_ACCESSIBLE_HOSTS.

        Ask Yourself Whether

        • Your WordPress website contains code which may call external requests to servers you don’t know.
        • Your WordPress website may send sensitive data to other servers.
        • Your WordPress website uses a lot of plugins or themes.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Uninstall WordPress plugins which send requests to servers you don’t know.
        • Make sure that WP_HTTP_BLOCK_EXTERNAL is defined in wp-config.php.
        • Make sure that WP_HTTP_BLOCK_EXTERNAL is set to true.
        • Make sure that WP_ACCESSIBLE_HOSTS is configured to authorize requests to the servers you trust.

        Sensitive Code Example

        define( 'WP_HTTP_BLOCK_EXTERNAL', false ); // Sensitive
        

        Compliant Solution

        define( 'WP_HTTP_BLOCK_EXTERNAL', true );
        define( 'WP_ACCESSIBLE_HOSTS', 'api.wordpress.org' );
        

        See

        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP - Top 10 2021 Category A10 - Server-Side Request Forgery (SSRF)
        • wordpress.org - Block External URL Requests
        • OWASP - Top 10 2017 Category A6 - Security Misconfiguration
        • OWASP Attack Category - Server Side Request Forgery
        • CWE - CWE-918 - Server-Side Request Forgery (SSRF)
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use